The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	May 9, 2026 11:05pm

PR Summary

Medium Risk
Touches multiple Zustand selectors and store access patterns in workflow UI, which can affect render frequency and state updates during workflow loading. Adds a new CI gate that can fail builds if selector patterns are flagged, so false positives could block merges.

Overview
Prevents Zustand v5 selector instability in the workflow UI by tightening store subscriptions (favoring field-level selectors) and wrapping multi-field selections in useShallow / useStoreWithEqualityFn to avoid fresh object/array allocations that can trigger rerender loops.

Adds stable empty fallback constants for sub-block values (EMPTY_SUBBLOCK_VALUES, EMPTY_BLOCK_SUBBLOCK_VALUES) and updates call sites to use them instead of inline {} defaults.

Introduces a new check:zustand-v5 script plus a CI step to audit unsafe selector patterns, and updates contract/codegen scripts to run generated output through a shared Biome formatter helper for consistent diffs.

^{Reviewed by Cursor Bugbot for commit 8ca96c2. Configure here.}

Greptile Summary

This PR addresses Zustand v5 selector stability regressions that could cause infinite render loops during workflow loading, by tightening store subscriptions across several components and adding a CI script to prevent future regressions.

• Selector fixes: Whole-store destructuring calls (useWorkflowRegistry(), useWorkflowStore(...)) are replaced with field-specific selectors or useShallow-wrapped selectors; inline {} and [] fallbacks are replaced with module-level stable constants (EMPTY_SUBBLOCK_VALUES, EMPTY_BLOCK_SUBBLOCK_VALUES, EMPTY_VARIABLES).
• CI audit: scripts/check-zustand-v5-selectors.ts is a new static analysis script that detects unsafe patterns (whole-store subscriptions, fresh object/array returns, unstable fallback literals) via regex and paren-matching, with a // zustand-v5-safe: <reason> escape hatch for intentional exceptions.
• Tooling: scripts/format-generated-source.ts centralizes biome formatting for generated files, and all sync scripts now run their output through it (driving the bulk key-reformatting in tool-schemas-v1.ts).

Confidence Score: 5/5

Safe to merge — all application changes are targeted subscription narrowing with no behavioral side-effects, and the new CI script is additive.

Each component change is a mechanical narrowing of an existing subscription: replacing whole-store destructuring with a field selector, or wrapping a returned object with useShallow for shallow comparison. The module-level empty constants correctly fix the root cause of reference instability. The useShallow(useCallback(..., [blockId])) composition is valid: useCallback memoizes on [blockId], and useShallow's internal useCallback depends on the outer selector reference, so the wrapped function only changes when blockId changes. No logic paths were altered, only re-render trigger conditions.

No files require special attention. The check-zustand-v5-selectors.ts script has minor edge cases around template-literal interpolation tracking and .reduce() false positives that have already been discussed on the PR.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Component renders] --> B{Zustand store hook call}
    B -->|Whole-store subscription before PR| C[Subscribe to entire store]
    B -->|Field-specific selector after PR| D[Subscribe to only needed fields]
    C --> E[Any state change triggers re-render]
    D --> F{Selector returns fresh object/array?}
    F -->|Yes - BEFORE fix| G[New reference every render - re-render loop]
    F -->|No - stable primitive or useShallow-wrapped| H[Shallow equality check - skip re-render if same values]
    H --> I[Stable render]

_{Reviews (2): Last reviewed commit: "address comments" | Re-trigger Greptile}

@greptile

bugbot run